-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update LICENSE-UNICODE text #28
Conversation
I'm unsure where the LICENSE-UNICODE text in this repo originated, but it's fairly different from the [canonical text](https://spdx.org/licenses/Unicode-DFS-2016.html) in the SPDX license list, so this updates it to match. The reason for this change is that the Unicode-3.0 license was added recently, which can actually be a [closer match](EmbarkStudios/cargo-about#267) to the current text, resulting in the SPDX identifier mismatching the actual one this crate is licensed under.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original is from https://web.archive.org/web/20220118205616/https://www.unicode.org/license.txt. As far as I know, this is the canonical rendering of Unicode-DFS-2016, provided directly by Unicode. The LICENSE-UNICODE file in this repo is byte identical to that one. The Rust standard library also uses the same in https://github.com/rust-lang/rust/blob/1.82.0/COPYRIGHT#L346-L391.
I would prefer if this were fixed in SPDX.
According to archive.org, the content of https://unicode.org/license.txt was swapped out from "UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE" to "UNICODE LICENSE V3" between the dates 2023.06.03 and 2023.09.11, which means between Unicode 15.0.0 (2022.09.13) and Unicode 15.1.0 (2023.09.12). A license wording change is not mentioned in the 15.1.0 release summary or announcement post. But I guess we are intended to infer that data files from Unicode 15.1.0 should be specified as licensed Unicode-3.0 as opposed to Unicode-DFS-2016. |
Yah, that's unfortunate lack of/ambiguous communication on their end, I've updated the text/references to Unicode-3.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I've sent a post regarding this issue to the "legal" mailing list for the Fedora Project. Red Hat lawyers are involved with SPDX upstream, maybe they can provide more insights: https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org/thread/CHVW3EPLVQYH6SSVAOLOZJAVBXCGWOR5/ |
Unicode changed its license between versions 15.0.0 and 15.1.0, from Unicode-DFS-2016 to Unicode-3.0. dtolnay/unicode-ident#28
Unicode changed its license between versions 15.0.0 and 15.1.0, from Unicode-DFS-2016 to Unicode-3.0. dtolnay/unicode-ident#28
Unicode changed its license between versions 15.0.0 and 15.1.0, from Unicode-DFS-2016 to Unicode-3.0. dtolnay/unicode-ident#28
See dtolnay/unicode-ident#28. TL;DR: unicode-ident now requires the Unicode 3.0 license, so this commit updates deny.toml to allow this rather than Unicode-DFs-2016.
I'm unsure where the LICENSE-UNICODE text in this repo originated, but it's fairly different from the canonical text in the SPDX license list, so this updates it to match.
The reason for this change is that the Unicode-3.0 license was added recently, which can actually be a closer match to the current text, resulting in the SPDX identifier mismatching the actual one this crate is licensed under.